Conversation
release-it runs `npm whoami` before publishing, which fails under OIDC because the auth token is only available during `npm publish --provenance`. Skip the pre-flight check so the OIDC token exchange happens at publish time as designed. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
"skipChecks": trueto thenpmsection of.release-it.json.Why
release-it runs
npm whoamias a pre-flight check before publishing. Under OIDC trusted publishing, no static auth token exists — the token is generated duringnpm publish --provenancevia the GitHub Actions OIDC provider. The pre-check fails because it runs before the token exchange happens. Skipping it lets the publish step handle authentication at the right time.Risk Assessment
Low risk. Single config addition. The npm registry still validates credentials during the actual publish step.
References